Skip to content
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

[CT-282] Implement better way of handling target attributes for deps and clean commands #4780

Closed
gshank opened this issue Feb 24, 2022 · 2 comments
Labels
stale Issues that have gone stale tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality

Comments

@gshank
Copy link
Contributor

gshank commented Feb 24, 2022

In ticket #4752 and pull request #4758 we implemented a quick fix for customers with references to target attributes in the jinja of their config files. We also have an issue with a poor error message for cases where users have typos in the target attributes. We should look at better ways of handling these two things, possibly by limiting config reading or a more-full-fledged no-profile target class. If an attribute does not exist, we should throw a reasonable error message.

@github-actions github-actions bot changed the title Implement better way of handling target attributes for deps and clean commands [CT-282] Implement better way of handling target attributes for deps and clean commands Feb 24, 2022
@jtcohen6 jtcohen6 added the tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality label Feb 25, 2022
@github-actions
Copy link
Contributor

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.

@github-actions github-actions bot added the stale Issues that have gone stale label Aug 25, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Sep 1, 2022

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest; add a comment to notify the maintainers.

@github-actions github-actions bot closed this as completed Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues that have gone stale tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality
Projects
None yet
Development

No branches or pull requests

2 participants