Skip to content

As a team, we want to make our code available to other potential users so that it will be a help to the community #14

Description

@baskaufs

Issue #3 was somewhat spinning out of control by becoming what was actually three issues. I already split off one of them into Issue #13 (related to retrieval of configuration variables) and left the issue of secure credentials in the original issue.

This issue is focused on how we would make or transform our code to be generic enough that it can be used by others. I'm going to reference comments that I made in Issue #3 relative to this.

On the level of documenting a lambda using a serverless application model (SAM) script, the Fn::Sub command can be used.

This comment and this comment discuss deployment of applications from the Serverless Application Repository (SAR) that have been made implementation-independent.

This comment discusses making the code implementation-independent at the time of building the application by building the policies and roles from a Python script rather than in the online GUI. The script is independent of the account number since that is inferred from the user credentials.

Finally, this comment discusses the issue of step functions not (yet) being able to be described by SAM and implications of how we should build our code.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions