Change scope of Azure API Mgmt Subscription - azure-api-management

I have a dozen or so subscriptions in Azure API Mgmt portal pointing to a scope of "API". But we will soon be updating to a new version, and I need to migrate these subscriptions as needed to v2. Is there a way to change the scope of an API Mgmt Subscription?

Generally, you'll have available both of your APIs and let your subscribers migrate to your new version in their own time, and eventually, you'd depreciate your oldest version as you release newer versions.

You could use REST API do do the job, see "scope" here: https://learn.microsoft.com/en-us/rest/api/apimanagement/2019-01-01/subscription/update.

Related

Azure APIM Prod and Non-Prod on single instance

Is it possible to have logical separation of Azure APIM service i.e one could work like Prod and Non-Prod at the same time?
If you check this Azure API Management DevOps Resource you would find that Microsoft recommends to use separate Azure API Management service instances for various environments, such as production, development, and QA. Where these environments are generally shared by multiple development teams, each responsible for a subset of APIs. It is the best practice for the enterprise setup.
But if you don't want to create multiple instances then, you could try using versions and revisions.
You can create revisions by right clicking API and click "Add Revision".
Similarly you can create versions by right clicking API and click "Add Version".
For more information check this answer by #DSpirit on the similar problem shared in Stack Overflow.

When Spring Data Couchbase and Syncgateway Couchbase would support named scopes or collection

Please find below a question on the Couchbase product roadmap.
CONTEXT
I am currently working on a feature to turn an existing system (a backend app and a mobile app) into a multi-tenant app.
The stack would be :
Couchbase 7.0
Spring Boot 2.5.5
Spring Data Couchbase : 4.2.5
SyncGateway : 2.8
PROBLEM
As far as I read in the documentation a good practice would be to use the new Couchbase 7.0 feature : Scopes and Collection.
However, everything does not seem to be ready :
The theory :
https://blog.couchbase.com/scopes-and-collections-for-modern-multi-tenant-applications-couchbase-7-0/
https://blog.couchbase.com/how-to-migrate-to-scopes-and-collections-in-couchbase-7-0/ and
In practice :
1- Spring Data Couchbase is (v4.2.5) not release yet to work with named scopes or collections
https://docs.spring.io/spring-data/couchbase/docs/4.2.5/reference/html/#reference
4.3.0-M3 github example give #Collection annotation which work but are not mentionned in the documentation.
2- Couchbase SyncGateway 2.8 is not compatible and 3.0 documentation does not mention a compatibility
Sync Gateway offers support for Couchbase Server’s default scopes and collections (Default Collections).
It does not currently support named scopes or collections (Named Collections).
https://docs.couchbase.com/sync-gateway/current/server-compatibility-collections.html#using-collections
QUESTIONS
To plan the project, or change the data structure (for example just using buckets) do you know when the full stack would be compatible with named scopes and collections ?
Do you know when Spring Data Couchbase 4.3.0 would be released (because 4.3.0-M3 version seems to be ok) ?
Do you know when a Syncgateway version compatible with named Scopes and Collections would be released ?
Thank you very much for your help.
Regards,
Matthieu.
Spring Data Couchbase 4.3.0 with Collections support is scheduled to be released on November 12. The try-cb-spring sample uses collections. I can't speak for Sync Gateway.
Mike
Named scopes and collections support on Sync Gateway is on our radar. We do not have a publicly available timeline at this point.
Note that until that is supported, there are alternate ways to deploy multi-tenant applications using Sync Gateway. You can point sync gateway databases to separate buckets or use the type value prefix pattern to segregate documents by tenant.
The new configuration approach in Sync Gateway 3.0 (beta) simplifies the administration of multi-tenant deployments by allowing sync gateway database configuration for tenants to be managed independent of each of other.
#MattMatt - I'm not familiar with the syncgateway api - but all that is needed for collection support for n1ql/query is an http parameter query_context=default:<bucket-name>.<scope-name> (bucket-name and scope-name escaped separately with back-tics) and then instead of specifying the bucket-name in the query, specify the collection-name. If the syncgateway has an api to add 'raw' http parameters, that could be used for n1ql/query without specific collection support.

exchange web services and EOL

I am planning to access Office 365 mailbox and i want to know whether EWS 2.2 still valid or need to go with Graph API.
I am planning to create a backup solution . and need to know
Thanks
If at all possible, use the Graph API. EWS is in maintenance mode and we are no longer adding features to it. The only case where you would need to use EWS is if you app also needed to access legacy on-prem Exchange installs since REST wasn't available for previous versions.

2nd generation Google cloud SQL - App Engine

Delighted to see that you have rolled out 2nd generation cloud SQL in Beta. However, I see that it is not available yet to GAE projects. Can you estimate when this link will be enabled please? We are making some big infrastructural changes in our fancy system necessitated by the slowness of Generation 1 SQL, but will stick with cloud SQL if the change is not far off.
As of April 27, 2016 Second Generation connectivity to App Engine is supported.
OLD content:
The Cloud SQL team is actively working on adding App Engine support for Second Generation instances. Unfortunately I can't speak about specific dates, but we hope to make it available as soon as possible.
You can now connect to second generation Google Cloud SQL instances from App Engine apps. The connection string is slightly different from first generation instances (docs).
Open your SQL instance in the cloud console.
Under properties copy the "Instance connection name". Note that this is different to the 'name' of your instance and will probably follow the format project:region:instance.
It is normal for the UI to say "None" for authorized applications - you will still be able to connect from GAE. Note: the SQL instance and GAE app must be part of the same project.
Update: Don't have to be in the same project, you need to grant access if they are not in the same project. Ref: https://cloud.google.com/sql/docs/dev-access#gaev1-csqlv2-access
Example PHP connection code:
$con = "mysql:unix_socket=/cloudsql/CONNECTION_STRING_FROM_CONSOLE;dbname=some_db";
$this->db = new pdo($con, "root", "");
$this->db->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);

Is it possible to automate the submission of an application to the Windows Store?

I want to more rapidly release updates for my application. Is it possible to call Web APIs from the Windows store to publish updates to my Windows 10 apps directly to the Store without manual interaction?
As far as I know .. there's no official API from Microsoft for that, you could ask for that : https://wpdev.uservoice.com/forums/110705-universal-windows-platform .