Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

IBM Cloud instructions contain deprecated API names and are US-only

See original GitHub issue

(From a Slack conversation in carbon-tutorial channel)

Step 5 of the Carbon tutorial tells people to log into IBM cloud using There are a couple of problems with this:

  1. This is a deprecated name, and should be (see
  2. If people log into the ‘US South’ region (as above), they’ll only see spaces for the ‘US South’ region - and in fact will be told they have no organisations if they have no spaces in the ‘US South’ region. The number 1 source of difficulty with troubleshooting Carbon Tutorial issues in my FED branch - which isn’t US-based - has been getting this working. It would be helpful to add some documentation to say either that the users should log into whatever region their spaces are in OR that they need to create a space in the ‘US South’ region. If they don’t do either of those they will get a lot of confusing errors.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:14 (1 by maintainers)

github_iconTop GitHub Comments

RoystonScommented, Apr 19, 2020

@JoseMiguelTM Thanks. The issue I raised was about outdated documentation that’s also confusing if you’re not in the ‘US South’ region. I did manage to get my group all sorted back in July last year but the documentation remains outdated and confusing.

JoseMiguelTMcommented, Apr 19, 2020

I solved your problem running ibmcloud commands on shell and that works for me, only that I have an issue with deployed app (exactly the page shows an 403 error…) My steps for push to IBM Cloud are the following:

  1. ibmcloud login
  2. ibmcloud target -g MY_RESOURCE_GROUP
  3. ibmcloud target --cf
  4. ibmcloud cf
  5. ibmcloud cf push -f manifest.yml

And that’s all but I still have the issue with the deployed app… I think the problem is for using nginx instead of buildpacks but sincerely I don’t have any idea because I’m beginner on IBM Cloud I hope this experience helps on your deployment issue, good luck!

Read more comments on GitHub >

github_iconTop Results From Across the Web

API Deprecation - August 2022 - 2 Questions: | API Connect
Hello smart people,MY IBM CLOUD SETUP:I have a Cloudant Lite database. To call that database, I have two Cloud Functions API's:API-1 exists ...
Read more >
IBM Cloud Data Shield Deprecation
As of 10 November 2022, the IBM Cloud Data Shield service is deprecated. Be sure to keep the following dates in mind when...
Read more >
Deprecated and removed features - IBM
Feature Deprecated in Removed in Installation on IBM Cloud Private 19.0.2 19.0.3 IBM Cloud Automation Manager Not applicable 19.0.2 IBM Cloud Private Not applicable 19.0.2
Read more >
Stabilized, deprecated, and removed function - IBM
Product or category Affected item Status APIs ‑ Application management Deprec... APIs ‑ Application management Deprec... APIs ‑ platform‑identity‑manager GET /idmgmt/identity/api/v1/users//getHighestRole Deprec...
Read more >
General IBM Cloud CLI (ibmcloud) commands
The prerequisites can include one or more of the following actions: Docker: Install the Docker CLI. Endpoint: Use the ibmcloud api command to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found