I publish a collection in a particular postman workspace successfully. The issue is that when I view the documentation using the public link, I am able to switch to other environments that are used by other workspace.
How can I publish the particular environment I want so that other environments are not seen publicly?
For instance in this image I want only the first staging to be seen and both local and the second staging not present.
Select the specific environment you would like to publish with.
Oh no! all environments are visible publicly :(
Don't worry! share the link with others, they will only able to see the environment you have selected while publishing the doc.
The list of environments visible to you because you have logged in with your account.
Related
I have a colleague who built a database app using ReTool.
Since it has been built quite nice, we would like to publish it on our cloud space and make it accessible for more than just him.
But we can't find any information on how to publish the app, apart from the in-app settings, to publish it, but it is always a "preview" version.
Anyone has experience with this?
You can share your Retool app publicly via a public link, and embed it in an iFrame in other applications or web pages. In edit mode just click the "Share" button on the top right and select the "Public" tab. (This will render your app publicly.)
But It's good to know that the public apps are only available on the Business and Enterprise plans.
Check this link for detailed information.
You can also get the share app url from (...) menu.
Assume that there is an application, SPA, that uses Google OAuth2.0 to access the Google Drive API.
Reading the docs, the application flow seems familiar enough on the client-side specially with Google's JavaScript library for authentication. However, I have stumbled upon a roadblock during application registration phase.
When creating the credentials for our client application, I am redirected to fill out the form at the OAuth Consent Screen first. There, among other things it demands us to declare whether the application is in Testing or In Production phase, so it can decide whether the app will be available to everyone or to Test Users only.
Assume I create a project for our application and set it on testing at first and then change it to production once I am ready to publish (with a new set of credentials as well).
My question is this. What if development continues on the application for new features while one instance of the app is in production? During development and testing I would need to restrict the application to my Test Users alone. Since the OAuth consent screen is project specific, not credential specific, will I require multiple projects on the console for every environment in which the application is running?
As in,
Project MyAppTesting will permanently remain in testing mode and will denote our development/testing branch.
Project MyAppProduction is always in production and denotes my production branch.
Similarly for the mobile client:
A MyMobileAppDev project having credentials configured with the debug keystore hash
A MyMobileAppProd project having credentials configured with the production keystore hash.
(both sets of credentials share the same package name).
Is this the idiomatic way? I failed to find any documentation on the matter. Please advise.
What #JohnHanley stated is the best way and the best practice when deploying application/s in GCP.
You can create multiple projects and create different Oauth for each of the projects. Check out this link on service accounts.
In addition to that, there are also some pros and cons when it comes to billing.
Pros:
Users consider having multiple billing accounts with respective projects assigned for each account to be able to see their billing details separately. In this way you can monitor the billing for each of the respective projects for each account.
Cons:
Attaching all the projects to one billing account, however, the billing reports will show all of the sum of the cost for all the projects, but you can still use the filter menu to be able to see the charges for each project.
I have multiple GCP projects, And I want to setup a multi-projects monitoring workspace for my environment. I would like to add all un-monitored projects to the workspace that I have already created, but via an API so that this job is automated.
Via console I know that it's possible using this link's setup (https://cloud.google.com/monitoring/workspaces/create#add-monitored-project) But how can I achieve this via an API?
Please can someone provide any inputs here.
You can manage Dashboard via API, and list services in the workspace, but API does not support adding projects to a workspace.
You can find list of all API methods here.
If you think that functionality should be supported, you can file a Feature Request.
As per this doc, in order to create a connector to Microsoft Teams, I'm supposed to publish it to the store.
If I am to build an internal-facing, highly company-specific bot that notifies of specific events, which is obviously supposed to be private, is there a way of building it?
Am I missing something here? Is it really necessary to publish it to the store in order to have it working in my company's Teams account?
As per this helpful link,
When you're ready to share your Microsoft Teams apps, you have three options depending on who your target audience is.
Upload your app directly If your app only needs to be shared to your team, or a few individuals in your organization, you can share your app package and upload it directly.
Publish to your organizational app catalog You can share your app with your entire organization through your app catalog.
Publish to the public app store If your app is for everyone, you can publish it to our public app store. Depending on your goals, you might be eligible for marketing and sales assistance.
So, in this case, uploading the app directly is the answer.
I had deployed the test application on Production on Google Cloud via App Engine and i could not see the instance is being created as its serverless it could or it could not create the instance.
But I am concerned about the billing since the URL was still running like on :
Example: http://mytestproject-123456.appspot.com/
So I disabled the billing for the project and also the application from the App Engine settings.
Could someone please help or suggest.
Is any action still required to stop the billing if there is any since I had deployed the application on Production and the url was accessible.
1.And If delete the whole project will it work?
If yes please tell the process.
If you want to stop the app from serving requests and running instances, you can disable the application. This way you will not be getting billed for that. Basically, there is no need to delete a billing account or the project to just stop serving requests. Please be aware that you still might be charged for storage, or other GCP services that you are using if applicable.
I would say that you do not need to do anything else. For future reference, before deploying a service, a good practice is to test it locally before deploying and starting to serve requests from users.
I suppose you are talking about the Standard Environment; if i am right, you can see the number of instances by going in the console, choosing your project in the selection control on top of the page. After this, in the left column, select App Engine, and, in the page that shows up, you can see the instances tab. There you will find all the running instances, if any.
If you are using other resources, they will be billed accordingly. If you are not, disabling the application is all you need to protect yourself against unwanted billing.
Hope this helps.