Skip to content

Conversation

dannyshisler
Copy link
Contributor

The ServiceEndpoint output value for endpoints urls generated by the Serverless framework is being overwritten incorrectly by the serverless-step-functions plugin.

I've described the issue in detail here: #149

This PR changes the ServiceEndpoint generation for API gateway deployments to match the output generated by Serverless framework.

Copy link
Collaborator

@horike37 horike37 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dannyshisler
Thank you for take care of that 👍
LGTM 💯

@horike37 horike37 merged commit e7589bd into serverless-operations:master Oct 13, 2018
@brian-fivetalent
Copy link

brian-fivetalent commented Jun 11, 2019

With serverless-step-functions version 1.24.0 I am still seeing my cloudformation output as follows
https://{XXXX}.execute-api.us-west-2.amazonaws.com/devamazonaws.com/dev

I found this in the output cloudformation

  ServiceEndpoint:
    Description: URL of the service endpoint
    Value: !Join 
      - ''
      - - 'https://'
        - !Ref ApiGatewayRestApi
        - .execute-api.us-west-2.
        - !Ref 'AWS::URLSuffix'
        - /dev
        - !Ref 'AWS::URLSuffix'
        - /dev

EDIT for anyone still finding this I had to run

serverless plugin uninstall --name serverless-step-functions

serverless plugin install --name serverless-step-functions and

sls deploy --force

EDIT EDIT I am still running into the issue when AWS code-build runs all three of the above functions. Using a Linux Container with Node 8

@theburningmonk
Copy link
Collaborator

@brian-fivetalent verified the issue and got a fix coming up

@theburningmonk
Copy link
Collaborator

@brian-fivetalent try again on 1.24.1

@brian-fivetalent
Copy link

@theburningmonk thank you! With 1.24.1 it is working as expected.

ss-betseqnzr pushed a commit to BetSEQNZR/serverless-step-functions that referenced this pull request Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants