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

Attributes: On update, should attributes be able to have all properties changed? #62

Closed
jrschumacher opened this issue Jan 23, 2024 · 3 comments
Labels
comp:architecture Anything that impacts architecture help wanted Extra attention is needed question Further information is requested

Comments

@jrschumacher
Copy link
Member

During the update process, should attributes be able to have all properties changed?

  • What happens if an attribute is in demo.com and is moved to example.com namespace?
  • What happens if an attribute rule is changed from ANY_OF to ALL_OF?
@jrschumacher jrschumacher added question Further information is requested help wanted Extra attention is needed labels Jan 23, 2024
@jrschumacher
Copy link
Member Author

@biscoe916 feels that we should not enable the mutability of an attribute namespace. If we need this feature, then we should have a specific RPC that will enable you to change it, but this would be an advanced feature.

There needs to be two paths:

  1. Special RPCs for specific dangerous operations
  2. Muck with the DB directly

@jrschumacher
Copy link
Member Author

@cassandrabailey293 @biscoe916 feedback:

mutable

  • rule

special RPC

  • attribute name

muck with DB

  • namespace

@jrschumacher
Copy link
Member Author

This will be resolved with #96 and #108

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp:architecture Anything that impacts architecture help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant