-
Notifications
You must be signed in to change notification settings - Fork 15
CLOUDP-262013: Upload local Collection to Postman #87
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
Conversation
| {"key": "digestAuthPassword", "value": "<string>"}, | ||
| {"key": "realm", "value": "<string>"}]' intermediate1.json > "$COLLECTION_TRANSFORMED_FILE_NAME" | ||
| else | ||
| cp intermediate1.json "$COLLECTION_TRANSFORMED_FILE_NAME" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider naming that adds collection in the name. I do not mind any format. It can be even
| cp intermediate1.json "$COLLECTION_TRANSFORMED_FILE_NAME" | |
| cp advancedCollection1.json "$COLLECTION_TRANSFORMED_FILE_NAME" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
renamed to intermediateCollection
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bit of a nit; but As a general good practice it might be better to use more meaningful separation of names:
intermediateCollectionUnmodified, intermediateCollectionNoQueryParams, intermediateCollectionNoPostmanId etc
matt-condon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non-blocking comment - LGTM
Proposed changes
Adds two scripts to allow the local postman collection to be uploaded to Postman:
Jira ticket: CLOUDP-262013
Checklist
Further comments