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

Don't rely on subscription configuration to get subscription name #352

Merged
merged 1 commit into from
Jan 18, 2024

Conversation

vincentbernat
Copy link
Contributor

When using the API directly, there is not subscription configuration (it is set in the app module) and we cannot use it to get the name. Instead, use the name provided in the function call.

This is a regression introduced in #331.

I am a bit unsure if this is the only regression as my tests are now failing. I am just quickly firing this one so you don't work on my comments in #331 in parallel.

When using the API directly, there is not subscription configuration (it
is set in the app module) and we cannot use it to get the name. Instead,
use the name provided in the function call.

This is a regression introduced in openconfig#331.
@vincentbernat
Copy link
Contributor Author

This PR is now OK for me.

@karimra
Copy link
Collaborator

karimra commented Jan 18, 2024

Thanks for the contribution!

@karimra karimra merged commit 7561948 into openconfig:main Jan 18, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants