-
Notifications
You must be signed in to change notification settings - Fork 21
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
oci-public-ip -j doesn't print valid json, -g has extra text #154
Comments
The message on using the stun servers is not warning, it is informational, in situations where you cannot get the public ip data from OCI, it falls back to scanning, which does not guarantee all data is found. Utility for displaying the public IP address of the current OCI instance. optional arguments: |
Ok, it's informational but it should still go to stderr imo. If Am I correct in assuming the ability to get public ip data "from OCI" means there's an instance principal (or similar) to allow API calls? I would say the base case of just having created an instance is the simpler situation and should give valid json even if it's not guaranteed.
|
I agree it the information should go to stderr; oci-public-ip -S stun.stunprotocol.org --output-mode json|jq[ |
In some situations, it looks like warning messages are getting sent to stdout when they should maybe get sent to stderr.
I don't know why this warning appears either, as it's a vanilla instance in IAD with 1 vnic. Actual ip obfuscated.
The text was updated successfully, but these errors were encountered: