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

feat: add createdAt and createdBy to project #422

Merged
merged 5 commits into from
May 31, 2024

Conversation

shubhindia
Copy link
Contributor

@shubhindia shubhindia commented May 23, 2024

Motivation

Right now there is no info for the project about when it was created and who created it. We are developing some internal APIs to manage nobl9, and would love to get this info added.

Summary

I have added relevant fields to the Project struct, the core controller needs to populate these fields, but since it isn't open-source, I can't do that myself.
@nieomylnieja Let me know your thoughts 😄

Release Notes

Added createdAt and createdBy fields to v1alpha Project.
These fields are not yet populated by the API, follow our release notes to get informed when the API support ships.

Signed-off-by: shubhindia <shubhindia123@gmail.com>
@shubhindia shubhindia changed the title add createdAt and createdBy to project as well feat: add createdAt and createdBy to project as well May 23, 2024
@shubhindia shubhindia changed the title feat: add createdAt and createdBy to project as well feat: add createdAt and createdBy to project May 23, 2024
@nieomylnieja
Copy link
Collaborator

nieomylnieja commented May 29, 2024

hey @shubhindia ;)

This is certainly doable, we need to consult this idea in our team responsible for object's API though :)
If we're to add that to Project, we should include that for all of our objects too, especially since SLO already has it.

I'll let you know once we have some thoughts/details on this one, thanks for bringing this up!

@shubhindia
Copy link
Contributor Author

shubhindia commented May 29, 2024

hey @shubhindia ;)

This is certainly doable, we need to consult this idea in our team responsible for object's API though :) If we're to add that to Project, we should include that for all of our objects too, especially since SLO already has it.

I'll let you know once we have some thoughts/details on this one, thanks for bringing this up!

Yup. Ideally it should be available for all the objects, but since I was working on projects, I added for them. Let me know if you guys decide to add it for other objects too. Happy to make that change here 😄

@nieomylnieja
Copy link
Collaborator

We talked through this today and we'd want to support those fields on most of our objects.
Since you're only interested in Project right now, I'd limit this PR scope to it alone.

I'll work on the changes for our internal system to support returning these fields, once that's done we'll merge this one.

Afterwards I'll work on extending support for these fields for other objects as well :)

@shubhindia
Copy link
Contributor Author

We talked through this today and we'd want to support those fields on most of our objects. Since you're only interested in Project right now, I'd limit this PR scope to it alone.

I'll work on the changes for our internal system to support returning these fields, once that's done we'll merge this one.

Afterwards I'll work on extending support for these fields for other objects as well :)

Cool. Sounds good 😁

Copy link
Collaborator

@nieomylnieja nieomylnieja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks once again for the idea and contribution :)
Once our platform ships with support for these fields I'll let you know!
You can also follow our release notes.

@nieomylnieja nieomylnieja enabled auto-merge (squash) May 31, 2024 15:31
@nieomylnieja nieomylnieja merged commit 8267e90 into nobl9:main May 31, 2024
13 checks passed
@nieomylnieja
Copy link
Collaborator

The changes are available in https://github.com/nobl9/nobl9-go/releases/tag/v0.82.0.

nieomylnieja added a commit to nobl9/sloctl that referenced this pull request Jun 11, 2024
…ct.Spec fields (#144)

## Motivation

With the introduction of new server-side computed fields for v1alpha
Project.Spec: `createdAt` and `createdBy` the tests started failing as
the helper function `_assert_objects_existence` was comparing almost the
whole object.
This is too much for a simple assertion that checks if the object was
actually applied, so I added additional filter to re-map the objects,
extracting the basic minimum for comparison.

## Related Changes

- nobl9/nobl9-go#422

## Testing

Run `make test/e2e`, remember about supplying the right env vars OR run
https://github.com/nobl9/sloctl/actions/workflows/e2e-tests-dispatch.yml
with this branch as target.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants