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

Set version of AST in a config file #1509

Open
1 task
james-garriss opened this issue Jan 9, 2025 · 0 comments
Open
1 task

Set version of AST in a config file #1509

james-garriss opened this issue Jan 9, 2025 · 0 comments
Labels
enhancement This issue or pull request will add new or improve existing functionality infrastructure Related to configuring infrastructure necessary for the project
Milestone

Comments

@james-garriss
Copy link
Collaborator

💡 Summary

Currently the version of Azure Sign Tool (AST) that is used for signing is hard-coded in a workflow. It's being moved into a PowerShell version. The version installed should be specified in some sort of config file or constants file.

This is related to epic #1136 and issue #1140.

Motivation and context

This type of information should be found in one file that everyone can see and use.

Implementation notes

This issue should not reinvent the wheel. Whatever solution is created in #1140 should simply be reused here.
The code that installs AST should use the value in the config/constants file.

Acceptance criteria

How do we know when this work is done?

  • The version of AST that is installed is no longer hard-coded.
@james-garriss james-garriss added enhancement This issue or pull request will add new or improve existing functionality infrastructure Related to configuring infrastructure necessary for the project labels Jan 9, 2025
@schrolla schrolla modified the milestones: Marlin, Backlog Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement This issue or pull request will add new or improve existing functionality infrastructure Related to configuring infrastructure necessary for the project
Projects
None yet
Development

No branches or pull requests

2 participants