Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for serverless v3 #51

Open
pokryfka opened this issue Oct 29, 2022 · 4 comments
Open

Support for serverless v3 #51

pokryfka opened this issue Oct 29, 2022 · 4 comments

Comments

@pokryfka
Copy link

Has the plugin been tested with serverless v3?

I just updated to serverless v3 and noticed a few issues:

environment values at function level are not exported, for example:

provider:
  environment:
    TEST1 = 1 # exported

functions:
  testFunc:
    environment:
       TEST2 = 2 # NOT exported
  1. Outputs are not exported, for example:
  - Outputs:
      AwsRegion:
        Value: ${self:custom.region} # NOT exported
  1. Resolving of some properties does not work anymore, in my case:
  • !GetAtt RedisReplicationGroup.PrimaryEndPoint.Address
  • !GetAtt GraphQlApi.GraphQLUrl

stopped working, which is reported as:

Fn::GetAttResolvers not found in params file: RedisReplicationGroup.PrimaryEndPoint.Address
Fn::GetAttResolvers not found in params file: devGraphQlApi.GraphQLUrl
@pelssersconsultancy
Copy link

I am experiencing the same issue

@rennehir
Copy link

Anyone managed to get this plugin working on v3? Or does someone have any other solutions similar to this?

I have multiple stacks, some of which export some values used in other stacks. Namely I have stacks for db and auth related things which export values and references to be used with the api stack. And I use serverless-offline to run the api stack locally. This plugin did the job in another project before upgrading to Serverless v3.

@zirkelc
Copy link

zirkelc commented Feb 14, 2024

I created an alternative plugin that works for me: https://github.com/zirkelc/serverless-exports-plugin

It exports the global environment variables and resource outputs during sls info and sls deploy. It's not feature complete with this plugin, mainly because I didn't require all of it.

@rennehir
Copy link

I actually managed to fix my issues by using ${cf:StackName.ExportName}

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

No branches or pull requests

4 participants