What is package.xml generated by illuminated cloud while deploying aura components or field level deployment.

[Nagendra Singh]

What is package.xml generated by illuminated cloud while deploying aura components or field level deployment.

Where can I see the package.xml locally generated via IC?

[Scott Wells]

I'm not 100% sure I understand the question. Are you asking where IC places the package.xml file that it generates when it performs a deployment via the Metadata API? If so, it's generated in-memory and stored in the deployment archive directly. It's never written into the filesystem as a distinct file. However, if you enable debug logging for metadata deployment as documented here:

http://www.illuminatedcloud.com/support/debuglogging

it will write the equivalent of the package.xml as a JSON object into the debug log so you can see what it's doing.

Does that help? If not just let me know what you're looking for and I'll be happy to help if possible.

[Nagendra Singh]

Yes that was exactly I was looking for, ok so as per logs you are using tooling API to deploy the single lightning file.

Because as per deployment documentation on aura, you cannot deploy it through ant migration tool, as single files cannot go in package.xml. Is my statement correct?

[Scott Wells]

Yes, that's correct. You can't deploy a single Aura bundle file using the Metadata API (which is what's used by the ant migration tool). If you tried to do so you'd end up with a bundle with just that single file. When you save changes to a single file from an Aura bundle, by default IC uses the Tooling REST API to PATCH that resource. If more than one file from an Aura bundle needs to be deployed alongside an Aura bundle file, the Metadata API must be used.

[Nagendra Singh]

So if we just include .cmp file along with any other aura component file it will deploy it correctly right?

[Scott Wells]

It seems like perhaps the core question is how to add an Aura component to a package.xml file, correct? If so, you just add the name of the component which is the same as the name of the directory in which the component files reside, e.g.:

    <types>
        <members>expenseList</members>
        <members>expenseTracker</members>
        <members>form</members>
        <members>updateExpenseItem</members>
        <name>AuraDefinitionBundle</name>
    </types>

Let me know if that's not what you're asking.

[Scott Wells]

I'm going to resolve this as it's more of a Q&A exercise. I'm happy to continue the discussion here, though.

[Nagendra Singh]

Yes this is what I was asking for, thanks. for closing the task.

[Nagendra Singh]

You said you used Tooling Rest API (Patch) for deploying the component,

Did you using Tooling API jar with JAVA or the normal API call, Like when doing through CURL we fire

curl https://login.salesforce.com/services/oauth2/token -d "grant_type=password" -d "client_id=********55M6SzOOELg7sfD4T6Pl" -d "client_secret=****" -d "username=${username}" -d "password=${password}"

and get the access token after which I pass it like this :

curl ${instanceFromRest}/services/data/v43.0/query?q=Select+Id+From+Account+LIMIT+5 -H "Authorization: Bearer ${access_token}" -H "X-PrettyPrint:1" 

I know the above is a get request, but even with workbench, how are you passing the updated file as PATCH request? Are you just passing the ID of the file ?

Can you please share some details on that front?

[Scott Wells]

Nagendra, since this request has moved from being about IC's functionality to how to interact with the Salesforce APIs for manipulating metadata, I'd first like to refer you to their documentation on the topic. Here's a general overview of how to interact with Tooling API objects using REST:

https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/intro_rest_overview.htm

and if you're specifically wanting to update a single Aura bundle file, I would also recommend you look at this:

https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/tooling_api_objects_auradefinition.htm