You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Overview of the Issue
Github autolinks are used to create hyperlinks of tickets.
For example, an autolink could be used for a case-insensitive string like WEB-123 to turn this into a markdown hyperlink of [WEB-123](https://someorg.atlassian.net/browse/WEB-123.
If this string happens to be in a resource address, then atlantis will throw an error because it does not strip the markdown from the comment.
i.e.
atlantis plan -- -target 'aws_route53_record["web-123"]'
will throw an error
Reproduction Steps
create an autolink in github repo for web-123
create a resource with an address containing the ticket
attempt a targeted plan
observe the error
Logs
Environment details
Additional Context
The text was updated successfully, but these errors were encountered:
Community Note
Overview of the Issue
Github autolinks are used to create hyperlinks of tickets.
For example, an autolink could be used for a case-insensitive string like
WEB-123
to turn this into a markdown hyperlink of[WEB-123](https://someorg.atlassian.net/browse/WEB-123
.If this string happens to be in a resource address, then atlantis will throw an error because it does not strip the markdown from the comment.
i.e.
will throw an error
Reproduction Steps
Logs
Environment details
Additional Context
The text was updated successfully, but these errors were encountered: