Skip to content

Linc Environment Variable substitution #18

@Nibblesh

Description

@Nibblesh

Is your feature request related to a problem? Please describe.

When we deploy our application we throw some build information into request headers so that we can trace the application version that causes issues.

While this is something that is fairly easy for custom deployments that use the lambda edge packager in CI/CD (by using the edgepackager's 3rd argument with environment variables), it becomes more difficult when handled by linc (some custom script needs to be written to add to the json file used in fab static build.)

Describe the solution you'd like
Variable substitution and a Legend of Linc variables that can be used in both the linc environments page, and in prod settings json or an alternative that allows us to access variables that the build would have information about.

If the feature is restricted to linc's UI, then maybe linc should have a config for default environment that is used in the 3rd argument of edgepackager, which allows the variable substitution

e.g.

{
  "RELEASE_URL": "{{ LINC_COMMIT_URL }}"
}

Additional context
I haven't thought through this too deeply, but we very much would like the FAB_SETTINGS object in our application to expose the git commit info from linc's build.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions