-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Blueprint] Prevent hidden artifacts parsing #4985
Merged
jsntcy
merged 1 commit into
Azure:main
from
simonkeyd:fix/prevent-blueprint-hidden-files-parsing
Jun 29, 2022
Merged
[Blueprint] Prevent hidden artifacts parsing #4985
jsntcy
merged 1 commit into
Azure:main
from
simonkeyd:fix/prevent-blueprint-hidden-files-parsing
Jun 29, 2022
Conversation
This file contains 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
ghost
added
the
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
label
Jun 13, 2022
Thank you for your contribution simonkeyd! We will review the pull request and get back to you soon. |
Blueprint |
jsntcy
reviewed
Jun 21, 2022
@simonkeyd, please take a look at my comments. |
Blueprint extension was parsing all files in the artifacts folder including hidden files. This unwanted behavior can also raise errors (eg. UnicodeDecodeError). This commit fixes this by preventing hidden Linux and Windows files from being parsed. closes Azure#4984
simonkeyd
force-pushed
the
fix/prevent-blueprint-hidden-files-parsing
branch
from
June 27, 2022 16:15
b99b68e
to
5392ed0
Compare
@jsntcy I amended my commit according to your suggestions. The code is now working for both Windows and Linux platforms. For Linux only it checks for files with a name starting with a dot and for Windows it excludes files with the hidden attribute. |
jsntcy
approved these changes
Jun 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
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.
Blueprint extension was parsing all files in the artifacts folder
including hidden Linux files. This unwanted behavior could also raise
errors (eg. UnicodeDecodeError). This commit fixes this by preventing
hidden files from being parsed.
closes #4984
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az blueprint import --name generic_blueprint --input-path ./generic_blueprint --management-group deadbeef-dead-beef-8badf00d1337
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally?About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.json
automatically.The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify
src/index.json
.