I had Created a resource element in IBM Cloud for NODE RED post loading it show dull.
I tried with different browsers and cleaned my cache, tried to delete resource and add another it didn't helped
Related
We have an older application based on the AppEngine SDK (now deprecated) and the superseded Cloud Datastore.
In the process of migrating to Google Cloud SDK we also decided to move from JPA/Datanucleus to Objectify.
Given that the Cloud Datastore will be automatically upgraded to Cloud Firestore in Datastore mode sometime in the future, we decided to test our application as described at the bottom of this page:
https://cloud.google.com/datastore/docs/upgrade-to-firestore#testing_an_existing_application
1) Create a new project. In this project, create a Cloud Firestore in Datastore mode database.
2) Using the managed export service, export some of your application's data to Cloud Storage.
3) Using the managed import service, import your application's data to your new project.
4) Copy app logic you want to test to the new project or simulate app behaviour against the new project.
That's what we did and after some issues we could make a portion of our application run fine with the new datastore in a separate test project.
Now to the actual issue...
We wanted to test if the updated application could also run with the superseded Cloud Datastore, so we won't have to worry when the automatic upgrade occurs (as our app will be already ready).
So we deployed it as a new version of the existing AppEngine project (v2-dot-.....): unfortunately running the new version throws a permission error as soon as the app tries to read the datastore:
com.google.cloud.datastore.DatastoreException: Missing or insufficient permissions
So the questions are:
- could this be related to the Cloud Datastore not being upgraded to Cloud Firestore in Datastore mode for our project yet?
- is there anything we can do (add specific permissions maybe) to make it work anyway?
Our concern is that we need to have the new version of the app deployed before July 2020 (that's when the older AppEngine SDK will stop working), and we are worried that the automatic upgrade of the datastore will occur later.
Thank you for your help.
Turned out our project doesn't have the PROJECT_ID#appspot.gserviceaccount.com member in IAM.
It has a pletora of other members (for example: PROJECT_NUMBER-compute#developer.gserviceaccount.com, PROJECT_NUMBER#cloudservices.gserviceaccount.com, service-PROJECT_NUMBER#compute-system.iam.gserviceaccount.com, etc) which I guess are legacy members used in previous versions of Google App Engine.
Adding PROJECT_ID#appspot.gserviceaccount.com with the role Editor fixed the issue: now the new version can be deployed to the old projects and it works fine even if the datastore has not yet been converted to Cloud Firestore in Datastore Mode.
I just ran into this issue and spent way too much time troubleshooting it. Nine times out of ten if you're running into this issue it's because the default App Engine service account doesn't have permission to edit Cloud Datastore. The default App Engine service account is used by default if you're doing a simple gcloud app deploy and nothing else fancy. I solved the problem by giving the default App Engine service account the roles/datastore.owner role with the following:
gcloud projects add-iam-policy-binding PROJECT_ID \
--member="serviceAccount:PROJECT_ID#appspot.gserviceaccount.com" \
--role="roles/datastore.owner"
I've got a Node-RED Dashboard running on Bluemix, but I want to secure it using the standard Node-RED security, i.e., editing the settings.js file.
Does anyone know how I can actually access this on BlueMix?
On the IBM Cloud dashboard for your application you need to enable the Continuous Delivery feature. That will get you a git repository containing the application code which you can edit in your browser and have changes automatically deploy back into your running application.
You will then need to edit the file called bluemix-settings.js to add the required settings to secure the Node-RED dashboard.
I am trying to create an application in IBM Internet of Things Platform Starter and getting following message:
BXNUI0005E: The 'xxxxxx' app wasn't created because a problem occurred contacting Cloud Foundry.
Try again later. If you see this message again, go to the IBM Cloud status page to check whether a service or component has an issue. If the problem continues, go to IBM Cloud Support.
I've had exactly the same problem. It's usually because you've gone over the limit of app / database instances for your account.
In my case, I was using NodeRed. I created one instance successfully, deleted it, but then couldn't create another. It turned out that the first app had created an empty database instance and the second one was trying to do the same. Deleting the database from my dashboard resolved the problem.
So I've read the documentation for enabling Plugins, but there doesn't seem to be a way to add new plugins other than for the ones already packaged.
I've tried grabbing the google cloud storage connector jar and sticking it in the 3rd party folder and starting Drill, but it doesn't seem to pick it up. I get an error that it doesn't recognise the protocol (gs://, as opposed to s3:// which works obviously).
Has any managed to do this? There seems to be zero information on getting this working, although Drill does claim to be able to work with google cloud services.
I have an old GAE application (in production since 2011) that use Cloud Storage service since it is available in beta. I have not touched this apps for almost 1 year now.
I have to do some administrative task and want to create new buckets in Cloud Storage.
I have activated
- the application in Google Cloud Console
- the billing for this application in Google Cloud Console
I see the Google Cloud Storage tab, when I click on it it is empty, and when I try to create a new bucket I see the error message:
The account for the specified project has been disabled.
How can I fix that?
Why I do not see my existing bucket? (created long time ago using the old Web interface)
Thanks!
This can happen when the Cloud Storage service isn't turned on for your project. Do the following:
Visit http://cloud.google.com/console
Select your project
Visit the APIs & Auth tab
Find Google Cloud Storage in the list of services
Turn on Google Cloud Storage
I was facing the same issue .While every API was enabled after deep diving i realized there is some problem relating to my billing.