Sign credentials in dev properties#187
Open
PerLundstrom-B3 wants to merge 4 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request contains two changes:
npx @sitevision/create-sitevision-appandnpm run setup-dev-propertiesnow allows the user to store credentials for developer.sitevision.se, which are used when signing an addon.npm run signnow reads these credentials from .dev-properties.json when available. If the credentials exist, signing completes without prompting the user. If they do not exist, the usual prompts for username, password, and certificate are shown.npm run signif the credentials exist in dev_properties:This will save a lot of time when signing addons, for example when you need to sign every addon when a use environment is moved to production.