add secrets for aziot test #1018
Closed
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
Signed-off-by: Shahriyar Jalayeri <[email protected]>
shjala
force-pushed
the
secrets_aziot_test
branch
from
aad37c5 to
b9b8d7d
Compare
Member
Author
|
closing this one, check #1019 |
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.
Aure-Iot-Edge test need access to some secrets to onboard a device into the Azure portal before testing, secrets are already added to the repository but #1011 fails to access them, according to Github documentation "GitHub Actions can only read a secret if you explicitly include the secret in a workflow."
Hope the syntax is correct.