question-mark
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.

VS Code Extensions missing Cloud Foundry params options

See original GitHub issue

Hello all. For VSCODE extensions, It does not look like all of the appropriate options are available via intellisense, and errors occur for those not included. For example including vars results in an error.:

  - put: cloud-foundry-g1
    params:
      vars:
        MYVAR: myvalue
      manifest: manifest.yml

This looks like where it would need to be added, although my familiarity with VS Code Extensions is limited.

https://github.com/spring-projects/sts4/blob/073d6fa98a5e518e4555440e345546437da9145b/headless-services/concourse-language-server/src/main/java/org/springframework/ide/vscode/concourse/PipelineYmlSchema.java#L736

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
mjnormancommented, Jul 26, 2019

This seems to be working fine, thanks for the quick update!

1reaction
mjnormancommented, Jul 22, 2019

Yes I didn’t want to bloat the issue, but you’re right I should be complete!

I see these as missing when comparing docs from original repo, https://github.com/concourse/cf-resource

Source attributes:

  • client_id: Optional. The client id used to authenticate.
  • client_secret: Optional. The client secret used to authenticate.
  • verbose: Optional. Invoke cf cli using CF_TRACE=true to print all API calls made to Cloud Foundry.

Param Attributes

  • vars: Optional. Map of variables to pass to manifest
  • vars_files: Optional. List of variables files to pass to manifest
  • docker_username: Optional. This is used as the username to authenticate against a protected docker registry.
  • docker_password: Optional. This should be the users password when authenticating against a protected docker registry.
  • show_app_log: Optional. Tails the app log during startup, useful to debug issues when using blue/green deploys together with the current_app_name option.
  • no_start: Optional. Deploys the app but does not start it. This parameter is ignored when current_app_name is specified.
Read more comments on GitHub >

github_iconTop Results From Across the Web

User and Workspace Settings - Visual Studio Code
The error can be as simple as a missing comma or incorrect setting value. Open the settings.json file with the Preferences: Open Settings...
Read more >
Managing Extensions in Visual Studio Code
Discover, add, update, disable and uninstall Visual Studio Code extensions (plug-ins) through the Extension Marketplace.
Read more >
April 2022 (version 1.67) - Visual Studio Code
Extension authors for enabling extensions that run code as web extensions (the list below is between March 28 2022 and May 1 2022):...
Read more >
April 2021 (version 1.56) - Visual Studio Code
Going forward, these settings are the recommended way to switch out the default ... VS Code prompts to install the Python extension if...
Read more >
August 2021 (version 1.60) - Visual Studio Code
Settings editor syntax highlighting - Rich syntax highlighting for setting ... Python extension testing updates - Better support for test discovery, ...
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 Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found