Blueprint Assist (Preview)The Blueprint Assist is an extension for VScode IDE. Some of its features are:
Prerequisites
ConfigurationYou can configure the Blueprint Assist Visual Studio Code extension, by accessing its settings. Accessing SettingsOpen the settings by finding Blueprint Assist in the extensions library and clicking on the gear icon. Note: "Manage" will appear when your mouse hovers over the gear icon. Click the "settings" menu option. This opens the Blueprint Assist settings in the editor window. Available SettingsLinting
Completions
General
Experimental
Getting StartedTo start with, click the Blueprint Assist (Preview) extension icon in the extension tray menu on the left. Click the "Sign In" button. Approve the dialogs that ensure you are aware you are signing in with a third party authentication service. If you are not already signed into Dell, you will be prompted in your browser. After you have been approved, return to Visual Studio Code. Approve the final dialog agreeing to use your Dell Identity session with the Blueprint Assist extension. You will now see the button to "Start Using a Blueprint Template". Click that button and a new blueprint will be opened in the Visual Studio Code editor. In the bottom margin of Visual Studio Code you should see that there is a check mark next to the word "Blueprint". Hover over that icon and you should see the services connection status. Configuring the Context for Complex BlueprintsSome blueprints span several files. Blueprint files can import other blueprint files. This means that resources referenced in the file in the current editor may be defined in a different file. This adds complexity for linting in particular. In order to tell blueprint assist where to look for relevant definitions, each blueprint project needs to contain a context file. This tutorial will explain how this is done. Make sure that you have saved your current blueprint, which will be called the "main" blueprint. Now create a new text file named ".dell.ba.context.yaml" in the same directory as your main blueprint. From now on this is called the "context file". You will need to define the main blueprint file's location in that context file. This tells the linter that in the current workspace "blueprint.yaml" is the main blueprint. Add the "definitions.yaml" file to have the main "blueprint_filename" set to "blueprint.yaml".
NOTE: Know that the more files you import, the more code sent to the linter, the slower the service will respond. Troubleshooting"I clicked the sign in button, but nothing happened."The symptom here is that you are clicking on the "Sign In" button, but nothing happens. This is often because an earlier sign in attempt failed, because the MFA or the SSO was interrupted. To resolve this issue, follow these steps:
"I clicked "Open Blueprint Assist", but nothing happened."The symptom here is that you are clicking on the "Open Blueprint Assist" button, but nothing happens. This is often because you do not have the Visual Studio Code extension for Github Copilot Chat, which is required. To resolve this issue, follow these steps:
"I wrote a message to @blueprint-assist chat participant and I received Language Model Unavailable error."Sometimes you might get the error "Language Model Unavailable". There are a few potential causes for this. Follow these trouble shooting instructions.
|